X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C86F6F.4E6C5AB4@onstor-exch02.onstor.net>; Thu, 14 Feb 2008 17:08:42 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C86F6F.4E6C5AB4"
Content-class: urn:content-classes:message
Subject: RE: Cougar to Bobcat migration strategy document for review
Date: Thu, 14 Feb 2008 17:08:42 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0856E7EF@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0856E7E0@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cougar to Bobcat migration strategy document for review
Thread-Index: AchpodZPB1Qz2CcxRe6MoPEft3LLGAFwsTqAAAIuT4AAAET/QA==
From: "Raj Kumar" <raj.kumar@onstor.com>
To: "Brian DeForest" <brian.deforest@onstor.com>,
	"Sripal Surendiran (HCL)" <sripal.surendiran@onstor.com>,
	"dl-Design Review" <dl-designreview@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C86F6F.4E6C5AB4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I think the main issue is whether the *required* downtime for this
migration is acceptable or not. If it's not acceptable then we will need
to workout a solution. I simply suggested BC-CG mixed cluster as a
solution which may or may not be feasible in cougar.=20

=20

I can not believe we can get customers to completely loose their
services for this long period. Or am I wrong? Probably marketing/support
folks will have better understanding about this situation than me.

=20

________________________________

From: Brian DeForest=20
Sent: Thursday, February 14, 2008 5:00 PM
To: Raj Kumar; Sripal Surendiran (HCL); dl-Design Review
Subject: RE: Cougar to Bobcat migration strategy document for review

=20

Supporting a mixed BC/CG cluster is not currently a requirement for
Cougar software.   If that were to become a new requirement, this
document would need to be revised to accomodate that.

=20

________________________________

From: Raj Kumar=20
Sent: Thursday, February 14, 2008 4:09 PM
To: Sripal Surendiran (HCL); dl-Design Review
Subject: RE: Cougar to Bobcat migration strategy document for review

Hi all,

=20

Is everybody ok with this requirement?

=20

1.	"Migration requires downtime of the entire Bobcat cluster.=20

=20

The following operation will add up to the total downtime while we
migrate from BC to CG.

=20

For Each node in a cluster:

=20

1.	Power down BC and take care removing all cables, label them,
remove power cable, flash cards, label them.=20
2.	Remove BC from the rack=20
3.	mount cougar=20
4.	Installing FP/FC cables and modifying MAC and rebooting it
again.=20
5.	Usual boot up time + updating config from 2ndry flash=20

=20

The above tasks can take anywhere between 50 minutes to 2 hours depends
on the racking conditions and/or labor skills/availability.=20

=20

If you have a 2 node, total down time: 1 hours 40 minutes to 4 hours

If you have 4 node: 3 hours 20 minutes to 8 hours.

=20

We need to be prepared for the worst case scenario as well. If for any
reason we run into some issues bringing up services in cougar, we will
need to revert back to BC. It will be the same time it takes to migrate
to cougar.

=20

Is this downtime acceptable?=20

=20

Did we consider some kind of rolling upgrade? Possibly supporting BC-CG
cluster just for upgrade purposes?

=20

Thanks.

=20

=20

________________________________

From: Sripal Surendiran (HCL)=20
Sent: Thursday, February 07, 2008 8:07 AM
To: dl-Design Review
Cc: Sripal Surendiran (HCL)
Subject: Cougar to Bobcat migration strategy document for review

=20

Hi all,

=20

PFA Bobcat to Cougar migration strategy functional specification
document. Please do respond me with your review comments.

=20

Regards,

Sripal.


------_=_NextPart_001_01C86F6F.4E6C5AB4
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:319768486;
	mso-list-template-ids:-928106482;}
@list l1
	{mso-list-id:2044552390;
	mso-list-template-ids:-2094754704;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I think the main issue is whether =
the *<b><span
style=3D'font-weight:bold'>required</span></b>* downtime for this =
migration is
acceptable or not. If it&#8217;s not acceptable then we will need to =
workout a
solution. I simply suggested BC-CG mixed cluster as a solution which may =
or may
not be feasible in cougar. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I can not believe we can get =
customers to
completely loose their services for this long period. Or am I wrong? =
Probably
marketing/support folks will have better understanding about this =
situation
than me.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
<st1:PersonName
w:st=3D"on">Brian DeForest</st1:PersonName> <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, February =
14, 2008
5:00 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Raj Kumar; Sripal =
Surendiran
(HCL); dl-Design Review<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Cougar to =
Bobcat
migration strategy document for review</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Supporting a mixed BC/CG cluster is =
not
currently a requirement for Cougar software.&nbsp;&nbsp; If that were to =
become
a new requirement, this document would need to be revised to accomodate =
that.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Raj Kumar
<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, February =
14, 2008
4:09 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Sripal Surendiran =
(HCL);
dl-Design Review<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Cougar to =
Bobcat
migration strategy document for review</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Hi =
all,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Is everybody ok with this =
requirement?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<ol style=3D'margin-top:0in' start=3D1 type=3D1>
 <li class=3DMsoNormal style=3D'text-align:justify;mso-list:l1 level1 =
lfo1'><font
     size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
     Arial;color:navy'>&#8220;</span></font>Migration requires downtime =
of the
     entire Bobcat cluster. <o:p></o:p></li>
</ol>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>The following operation will add up =
to the
total downtime while we migrate from BC to =
CG.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>For Each node in a =
cluster:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<ol style=3D'margin-top:0in' start=3D1 type=3D1>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l0 level1 =
lfo2'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Power
     down BC and take care removing all cables, label them, remove power =
cable,
     flash cards, label them.</span></font> <font size=3D2 =
face=3DArial><span
     =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></l=
i>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l0 level1 =
lfo2'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Remove
     BC from the rack</span></font> <font size=3D2 face=3DArial><span
     =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></l=
i>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l0 level1 =
lfo2'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>mount
     cougar</span></font> <font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
     font-family:Arial'><o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l0 level1 =
lfo2'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Installing
     FP/FC cables and modifying MAC and rebooting it =
again.</span></font> <font
     size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></l=
i>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l0 level1 =
lfo2'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Usual
     boot up time + updating config from 2ndry flash</span></font> <font
     size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></l=
i>
</ol>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>The above tasks can take anywhere =
between
50 minutes to 2 hours depends on the racking conditions and/or labor
skills/availability. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>If you have a 2 node, total down =
time: 1
hours 40 minutes to 4 hours<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>If you have 4 node: 3 hours 20 =
minutes to
8 hours.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>We need to be prepared for the =
worst case
scenario as well. If for any reason we run into some issues bringing up
services in cougar, we will need to revert back to BC. It will be the =
same time
it takes to migrate to cougar.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Is this downtime acceptable? =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Did we consider some kind of =
rolling
upgrade? Possibly supporting BC-CG cluster just for upgrade =
purposes?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks.<o:p></o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Sripal
Surendiran (HCL) <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, February =
07, 2008
8:07 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> dl-Design Review<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> Sripal Surendiran =
(HCL)<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Cougar to Bobcat
migration strategy document for review</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Hi =
all,</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>PFA Bobcat to Cougar migration strategy functional
specification document. Please do respond me with your review =
comments.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Regards,</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Sripal.</span></font><o:p></o:p></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C86F6F.4E6C5AB4--
